⚡ Bolt: Add client-side caching to domain search#125
Conversation
- Implemented a Map-based cache in DomainSearch.svelte to store domain availability results. - Cache persists for 60 seconds (TTL). - Prevents redundant network requests when typing or correcting search queries. - Improves responsiveness by displaying cached results immediately. - Handles race conditions by invalidating pending requests on cache hit. Co-authored-by: yeboster <23556525+yeboster@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
1 participant
⚡ Bolt: Add client-side caching to domain search
💡 What: Implemented a client-side cache using a Map for domain search results in
DomainSearch.svelte. The cache stores results for 60 seconds.🎯 Why: The previous implementation triggered a network request for every debounced keystroke, even if the user had just searched for the same term (e.g., backspacing and retyping). This caused unnecessary load on the blockchain/SDK and slower feedback for the user.
📊 Impact:
🔬 Measurement: Verified using a Playwright script that counts network requests to
partisiablockchain.com. Confirmed that re-typing the same query triggers 0 new requests while still updating the UI correctly.PR created automatically by Jules for task 9843610027250588732 started by @yeboster